Method of low-bandwidth data transport

ABSTRACT

A method is disclosed for more efficiently and economically transporting data on a network using network access links between the first switch, which is the entry point of the network, and an end-user device, which is either on a fixed link on a customer premises or is a mobile device. The method includes terminating one or more protocol sessions at the first switch and removing corresponding packet headers. The first switch creates a substitute packet, adding a substitute header that identifies the transport path and the communications connection. Removed headers are not delivered to the end-user device which processes received substitute packets into usable streams based on the substitute header.

TECHNICAL FIELD

In the field of multiplex communications, a method is disclosed fororganizing information to be switched over a plurality of nodes whereone or more bytes of the information is preceded by an identificationinformation indicative of a source or destination station.

BACKGROUND ART

Virtual circuits are the basis of Frame Relay service and appear inrouter networks as Multi-Protocol Label Switching (MPLS) label switchedpaths (LSPs).

A Label Switched Path is defined by entries in flow tables that directarriving frames to their next onward destination. The Label need beunique only on a link; a value may be used by another connection on adifferent link. The Label on a packet may be changed by a switch duringa forwarding operation.

Multi-Protocol Label Switching and Label Switched Paths have beencontained within a carrier network. The “customer” never sees a label,only standard Internet Protocol (IP) and related headers. The size ofstandard headers make them significant consumers of bandwidth. Variousforms of header compression exist and apply mostly on one link, thoughthere are proposals (not yet usable in practice) to apply headercompression end-to-end over a Label Switched Path.

SUMMARY OF INVENTION

A method is disclosed for more efficiently and economically transportingdata on a network. The method includes providing network access linksthat include a plurality of switches where a first switch receives afirst packet from a first end-user device via an Internet Protocolsession. The first packet has a first header that includes an InternetProtocol header with an Internet Protocol address. The first switchterminates the Internet Protocol session and removes the InternetProtocol header from the first packet. The first switch then matches thefirst packet with flow-path data in a flow-table, which yields aphysical path containing a transport route from the first switch to thesecond end-user device. The first switch then generates a substitutepacket containing information from the first packet less the InternetProtocol header that was removed. The substitute packet further containsa path identifier that is an instruction on how to route the substitutepacket on the physical path in the plurality of switches to the secondend-user device. The substitute packet further contains a connectionidentifier that identifies multiple communications sessions that sharethe physical path from the first switch through the plurality ofswitches to the second end-user device. Finally, the substitute packetincludes control information on how to coordinate joint operation of thefirst switch and the second end-user device. The method next includes astep of transmitting the substitute packet, preferably in a frame thatincludes a Layer Two protocol such as Ethernet, along the physical paththrough the plurality of switches to the second end-user device. Thisthen causes the second end-user device to terminate the physical pathfor the substitute packet, match the connection identifier of thesubstitute packet to a communications session, and process thesubstitute packet into a usable stream. The usable stream is formed toexclude the Internet Protocol header previously removed from the firstpacket.

Optional steps in the method include receiving a usable data streamcomprising a plurality of packets; requiring the usable data stream toinclude one or more of an audio stream, a video stream, and applicationdata to be delivered to an application.

Optional steps further include requiring the transport route to be avirtual circuit involving a Multi-Protocol Label Switched (MPLS) path,an Ethernet subnet, a Frame Relay data link connection, or anAsynchronous Transfer Mode (ATM) virtual path.

Optional steps further include requiring the first packet to include asecond header with a transport-layer protocol header. Then, terminatinga transport-layer protocol session and deleting the second header whengenerating the substitute packet.

Optional steps further include requiring the first packet to includeadditional headers representing higher-level protocols, and thenterminating each protocol session corresponding to the one or moreadditional headers and removing at the first switch the one or moreadditional headers prior to generating the substitute packet.

Optional steps further include requiring the first packet to include apayload of information and then transmitting the payload of informationto the second end-user device with the substitute packet.

Optional steps further include receiving a frame at any switch in theplurality of switches; and enabling each switch in the plurality ofswitches to match the frame with flow-path data in the flow-table. Whenthe frame has been received, then when any of the plurality of switchesfails to match the frame with flow-path data in the flow-table eitherdiscarding the frame and/or sending an error message to the firstswitch.

Optional steps further include broadcasting a query seeking a flow-pathto the second end-user device when any of the plurality of switchesfails to match the first packet, or the substitute packet, withflow-path data. The broadcast is made to a connected device, such as arouter, a host, a switch, and/or a controller.

Optional steps further include enabling a connection of the secondend-user device to one of the switches in the plurality of switches. Theconnection may include an optical cable, an electrical cable, and aradio link.

Optional steps further include receiving at the first switch atransmission originating from a second end-user device. The transmissionincludes a path identifier and a connection identifier and thetransmission includes a header format defined in the substitute packet.Then, matching the transmission from the second end-user device withsecond flow-path data in the flow-table, the second flow-path datacomprising a transport route from the first switch to the first end-userdevice. Then, identifying an off-network device outside of the pluralityof switches, specifically the first end-user device. The secondflow-path data includes a transport route from the first switch to thefirst end-user device. Then, generating a second packet at the firstswitch. The second packet includes information from the transmissionreceived from the second end-user device. Then, adding to the secondpacket an Internet-Protocol-address header that participates in theInternet Protocol session terminated at the first switch after receivingthe first packet from the first end-user device and adding a header foreach higher-level protocol terminated from the first packet, each saidheader participating in a terminated session. Then, sending the secondpacket out of the plurality of switches to an end-user device,specifically the first end-user device. The first end-user device beinga terminal, a host, a router, and/or a bridge.

An optional step includes limiting the connection identifier to one of aMulti-Protocol Label Switched (MPLS) network Label, an Ethernet header,a Frame Relay Data Link Connection Identifier, and an AsynchronousTransfer Mode (ATM) network Virtual Path Identifier.

An alternative embodiment includes a step of providing network accesslinks comprising a plurality of switches, the plurality of switchescomprising a first switch, which in this embodiment is exemplified by arouter. This alternative embodiment further includes steps of: receivinga first packet at the first switch, the first packet comprising data,the data comprising a plurality of packet headers, the plurality ofpacket headers comprising a network-layer protocol, the network-layerprotocol comprising an Internet Protocol address; creating a reduceddata packet by terminating a higher-level protocol at the first switchand removing from the first packet at least one packet header in theplurality of packet headers other than the network-layer protocolcomprising the Internet Protocol address; generating a substitute packetat the first switch, the substitute packet comprising: the reduced datapacket; and a substitute header, the substitute header comprising: aconnection identifier comprising an instruction to identify thecommunication session; and control information comprising instructionson coordinating a joint operation of the first switch and the end-userdevice; transmitting the substitute packet via Internet Protocol routingusing the Internet Protocol address to the end-user device; and enablingthe end-user device to: derive a connection identity from the connectionidentifier and control information in the substitute header; and processthe substitute packet into a usable stream.

Technical Problem

Cellular radio links depend on scarce spectrum and pose bandwidthbottlenecks. To maximize efficient use of this resource, Voice OverLong-Term Evolution (VoLTE) applies Robust Header Compression (RoHC) toInternet Protocol packets on the radio link. Typically this compressionreduces layer 2 and 3 headers to 3 bytes, but does not affecthigher-level protocols. However, the compression and decompressionoperations impose processor loads in the radio base station and in themobile or radio device. Those operations also introduce additionallatency, which, for example, adversely affects the perceived soundquality of a voice connection.

The typical teaching in the prior art is that the “second switch”restores full headers to the payload before passing the packet to theend device. This results in significant consumption of bandwidth, largeprocessing time, and increased latency in accessing networks.

Solution to Problem

The solution is a method to significantly reduce bandwidth on networkaccess links such as the cellular radio access network, satellite hops,and lower-speed optical and electrical interfaces, without theprocessing loads.

At the same time, this invention provides the same advantages in packetforwarding and reduced latency in the access network that Multi-ProtocolLabel Switching provides in the core. Because the method disclosed usesthe same label format in all devices, the Label Switched Path featuresin routers and switches operate normally.

The savings afforded by the method disclosed apply in both directions oftransmission. The radio device, for example, prepares a payload to sendby applying only a short path label and a connection identifier in asubstitute header. There is no need for any headers containing InternetProtocol addresses.

Advantageous Effects of Invention

The method extends the Label Switched Path, previously restricted to thecarrier's autonomous region, into the end device: smartphone, tablet,personal computer (PC), television (TV), media player, etc. This isparticularly advantageous in cost and performance where the accessbandwidth is limited or expensive.

The devices listed above today receive packet data in the Internetformat: Internet Protocol header, then a Layer 3 header. Examplesinclude a Transmission Control Protocol (TCP) or User Datagram Protocol(UDP), and possibly other headers. On local networks, almost all packetsuse an Ethernet header in addition to the others.

Drawing on the features of Software Defined Network (SDN), the methoddisclosed allows a central controller to set up a virtual circuit notonly within the carrier network, but also throughout access facilities(radio, optical, or electrical) to the user device. This is advantageousbecause a central processor that calculates routing paths and sets upvirtual circuits relieves the network routers and switches of runningcomplex and processor-heavy protocols, such as Robust Header Compressionand gateway routing protocols.

Label Switched Paths are controlled by the central processor so theynormally cannot be changed by a user device. An application can requesta connection, but the controller verifies the authority of therequester. The method is particularly advantageous in enhancing securitybecause a device limited to connecting via Label Switched Paths can beguarded from intrusion and restricted in reach by policies applied inthe central controller.

BRIEF DESCRIPTION OF DRAWINGS

The drawings illustrate preferred embodiments of the method oflow-bandwidth data transport according to the disclosure. The referencenumbers in the drawings are used consistently throughout. New referencenumbers in FIG. 2 are given the 200 series numbers. Similarly, newreference numbers in each succeeding drawing are given a correspondingseries number beginning with the figure number.

FIG. 1 is a block diagram of the steps in a preferred embodiment of thelow-bandwidth data transport method.

FIG. 2 is a block diagram of optional steps in the method.

FIG. 3 is a block diagram of optional steps in the method.

FIG. 4 is a block diagram of an alternative embodiment of thelow-bandwidth data transport method.

DESCRIPTION OF EMBODIMENTS

In the following description, reference is made to the accompanyingdrawings, which form a part hereof and which illustrate severalembodiments of the present invention. The drawings and the preferredembodiments of the invention are presented with the understanding thatthe present invention is susceptible to performance of the steps in anyorder not contradicted by the express requirements of the claimed steps.Thus, other embodiments may be utilized with operational changes in theorder of steps, without departing from the scope of the presentinvention.

FIG. 1 is a block diagram of the steps in a preferred embodiment of thelow-bandwidth data transport process. Solid connecting lines between theblocks generally indicate required steps in the process. FIG. 1 shows aMethod (100) of transporting data on a network. The transport may be intwo directions, such as from a computer to a cell phone and back again.Thus, the transport may be in a first direction using network accesslinks from a first switch to a second end-user device and in a seconddirection from a second end-user device to the first switch and to thefirst end-user device.

An end-user device is exemplified by a cell phone, a desktop computer, atablet computer, a terminal, a switch, a router, or any other host. Ahost, as used in this application, includes any device having an IPaddress. For example, a host is most commonly a computer connected tothe Internet. While there is some overlap in the listing of thecomponents that constitute the end-user device, or infra, whendiscussing a “connected device,” this overlap is not intended to imply anarrow definition of any such listed component. Rather, it is intendedas an aid in understanding the scope the claimed invention.

The preferred method includes multiple steps identified as: a Providingstep (105); a Receiving step (110); a Terminating step (115); a Removingstep (120); a Matching step (125); an Identifying step (130); aGenerating step (135); and a Transmitting step (140).

The Providing step (105) includes providing network access linkscomprising a plurality of switches. The plurality of switches includes afirst switch. A network switch is also called a switching hub, abridging hub, a router, and a MAC bridge. A network switch is a computernetworking device that interconnects devices on a computer network byusing packet switching to receive, process, and forward data to thedestination device. The plurality of switches manages the flow of dataacross a network by transmitting a received network packet only to theone or more devices for which the packet is intended.

The Receiving step (110) includes receiving a first packet from a firstend-user device via an Internet Protocol session. The Receiving step(110) is performed at the first switch by operations at the firstswitch. The first packet includes a first header. The first headerincludes an Internet Protocol header and other headers may be also be apart of the first header. The Internet Protocol header includes anInternet Protocol address. It is noted that there is typically a sessionassociated with each header. Thus, an Internet Protocol header isreceived incident to an Internet Protocol session. It is the same withany other headers received during the Receiving step (110) or at othertimes in performance of the steps in the disclosed Method (100)

The Terminating step (115) includes terminating the Internet Protocolsession. Preferably, the first switch implements the Terminating step(115).

The Removing step (120) includes removing the Internet Protocol headerfrom the first packet. Preferably, the first switch implements theRemoving step (120).

The Matching step (125) includes matching the first packet withflow-path data in a flow-table. Preferably, the first switch implementsthe Matching step (125).

The Identifying step (130) includes identifying a physical path usingthe flow-path data matched to the first packet, the physical pathcomprising a transport route from the first switch to the secondend-user device. Preferably, the first switch implements the Identifyingstep (130).

The Generating step (135) includes generating a substitute packet at thefirst switch. The substitute packet is therefore created by operationsat the first switch on the first packet received after the Receivingstep (110).

The substitute packet includes information from the first packet thatwas not deleted from the first packet in the Removing step (120). Thus,the substitute packet includes information from the first packet thatremains after removal of Internet Protocol header from the first packet.

The substitute packet further includes a path identifier comprising aninstruction on how to route the substitute packet to the physical pathin the plurality of switches to the end-user device.

The substitute packet further includes a connection identifierconfigured to permit identifying multiple communications sessions thatshare the physical path from the first switch through the plurality ofswitches to the end-user device.

The substitute packet further includes control information comprisinginstructions on coordinating a joint operation of the first switch andthe end-user device.

The Transmitting step (140) includes transmitting the substitute packet,preferably in a frame that includes a Layer Two protocol, such asEthernet, along the physical path through the plurality of switches tothe second end-user device. Preferably, the first switch implements theTransmitting step (140).

The Transmitting step (140) further includes causing the end-user deviceto: terminate the physical path for the substitute packet. Theinstruction to the end-user device is preferably sent by the firstswitch. The Transmitting step (140) includes instructions for theend-user device to match the connection identifier of the substitutepacket to a communications session. The Transmitting step (140) furtherincludes an instruction for the end-user device to process thesubstitute packet into a usable stream. The usable stream is formed toexclude the Internet Protocol header previously removed from the firstpacket.

FIG. 2 discloses additional optional steps and optional limitations onthe steps disclosed in FIG. 1 that may be performed in the Method (100).Optional steps are generally indicated by a dashed line connecting theboxes. These optional steps and limitations include those identified as:a Usable stream step (202); an Audio limitation (203); a Videolimitation (204); a Data limitation (205); a Route limitation (206); aSecond header limitation (207); an Additional header limitation (208); aFirst packet limitation (209); a Payload transmittal step (210).

The Usable stream step (202) includes receiving a usable data streamcomprising a plurality of packets. This step is preferably performed bythe first switch.

The Audio limitation (203) requires that the usable data stream receivedin Usable stream step (202) include an audio stream.

The Video limitation (204) requires that the usable data stream receivedin Usable stream step (202) include a video stream.

The Data limitation (205) requires that the usable data stream receivedin Usable stream step (202) include application data to be delivered toan application.

The Route limitation (206) requires the transport route to be a virtualcircuit selected from the group consisting of a Multi-Protocol LabelSwitched (MPLS) path, an Ethernet subnet, a Frame Relay data linkconnection, and an Asynchronous Transfer Mode (ATM) virtual path. Anyvirtual circuit technology may be used.

The Second header limitation (207) requires the first packet to includea second header. The second header includes a transport-layer protocolheader. The Second header limitation (207) adds steps of terminating atransport-layer protocol session and deleting the second header whengenerating the substitute packet.

The Additional header limitation (208) requires that the first packetfurther include one or more additional headers representing higher-levelprotocols. The Additional header limitation (208) further includes thesteps of terminating each protocol session corresponding to the one ormore additional headers; and removing at the first switch the one ormore additional headers prior to generating the substitute packet.

The First packet limitation (209) requires that the first packet includea payload of information. A payload of information may be any data, butis typically useful information, such as a digitized communicationsmessage.

The Payload transmittal step (210) adds a step of transmitting thepayload of information to the second end-user device with the substitutepacket.

FIG. 3 is a block diagram of additional optional steps to thosedisclosed in FIG. 1 that may be performed in the Method (100). Optionalsteps are generally indicated by a dashed line connecting the boxes.These additional steps are identified as: Frame steps (311); a Framediscard step (312); an Error message step (313); a Querying step (314);an End-user connecting step (315); End-user communication steps (316);and a Connection identifier step (317)

The Frame steps (311) include steps of: receiving a frame at any switchin the plurality of switches; and enabling each switch in the pluralityof switches to match the frame with flow-path data in the flow-table.

The Frame discard step (312) adds a step to the Frame steps (311). Theadded step is discarding the frame when any of the plurality of switchesfails to match the frame with flow-path data in the flow-table.

The Error message step (313) adds a step of sending an error message tothe first switch when any switch in the plurality of switches fails tomatch the frame with flow-path data in the flow-table.

The Querying step (314) adds a step to the Frame steps (311). The addedstep is broadcasting a query seeking a flow-path to the end-user devicewhen any of the plurality of switches fails to match the first packetwith flow-path data. Broadcasting the query is made to a connecteddevice. Preferably, the connected device is one of a router, a switch,and a controller.

The End-user connecting step (315) adds a step to the Frame steps (311).The added step is enabling a connection of the end-user device to one ofthe switches in the plurality of switches. Preferably, the connection isone of an optical cable, an electrical cable, and a radio link.

The End-user communication steps (316) adds steps to the End-userconnecting step (315). The added steps define communication from thesecond end-user device to the first end-user device. The End-usercommunication steps (316) include: receiving at the first switch atransmission originating from a second end-user device, the transmissioncomprising a path identifier and a connection identifier, thetransmission employing a header format defined in the substitute packet;matching the transmission from the second end-user device with secondflow-path data in the flow-table, the second flow-path data comprising atransport route from the first switch to the first end-user device;generating a second packet at the first switch, the second packetcomprising information from the transmission received from the secondend-user device; adding to the second packet anInternet-Protocol-address header that participates in the InternetProtocol session terminated at the first switch after receiving thefirst packet from the first end-user device and a header for eachhigher-level protocol session terminated from the first packet; andsending the second packet out of the plurality of switches to the firstend-user device, the first end-user device selected from the groupconsisting of a terminal, a host, a router, a switch, and a bridge. Inone embodiment, the first switch does not include in the second packet apath identifier or a connection identifier, so the off-network enddevice, such as a first end-user device, does not have to deal withthem.

The Connection identifier step (317) adds a step to the End-usercommunication steps (316). The added step includes the step of limitingthe connection identifier to one selected from the group consisting of aMulti-Protocol Label Switched (MPLS) network Label, an Ethernet header,a Frame Relay Data Link Connection Identifier, and an AsynchronousTransfer Mode (ATM) network Virtual Path Identifier.

FIG. 4 is a block diagram of an alternative embodiment of the Method(100). Solid connecting lines between the blocks generally indicaterequired steps in the process. This alternative embodiment includessteps identified as: a Providing step (105); a Second receiving step(418); a Creating step (419); a Second generating step (420); a Secondtransmitting step (421); and End-user device step (422).

The Providing step (105) is the same as with the embodiment describedabove as the preferred embodiment. The Providing step (105) is providingnetwork access links comprising a plurality of switches, the pluralityof switches comprising a first switch. The first switch is bestexemplified in this alternative embodiment as a router.

The Second receiving step (418) includes a step of providing networkaccess links including a plurality of switches. The plurality ofswitches includes a first switch.

The Creating step (419) includes a step of receiving a first packet atthe first switch. The first packet includes data. Preferably, the dataincludes a plurality of packet headers. The plurality of packet headersinclude a network-layer protocol. The network-layer protocol includes aheader for the Internet Protocol, which contains an Internet Protocoladdress.

The Second generating step (420) includes steps of: creating a reduceddata packet by terminating a higher-level protocol at the first switchand removing from the first packet at least one packet header in theplurality of packet headers other than the network-layer protocolcomprising the Internet Protocol address. For example, in a general usecase, the first switch, when it generates the reduced data packet, willterminate a UDP session and remove a UDP header.

The Second generating step (420) includes a step of generating asubstitute packet at the first switch. The substitute packet includesthe reduced data packet; and a substitute header. The substitute headerincludes a connection identifier. The connection identifier contains aninstruction to identify a communication session. The substitute headerfurther includes control information having instructions on coordinatinga joint operation of the first switch and the end-user device.

The Second transmitting step (421) further includes a step oftransmitting the substitute packet via Internet Protocol routing usingthe Internet Protocol address to the end-user device.

The End-user device step (422) includes a step of enabling the end-userdevice to: derive a connection identity from the connection identifierand control information in the substitute header; and to process thesubstitute packet into a usable stream.

EXAMPLE

This example describes how a preferred exemplary method is implementedover a network that includes a controller; a first switch; a secondswitch; a base station containing a third switch, radio, and antenna;and a device that communicates by radio with the base station.

In this example, the first switch is configured to receive a frameencapsulating a first packet header and, optionally, a payload ofinformation. The first switch is further configured to compare the frameto a flow table. The first switch is also configured to respond tofinding no match in the flow table by sending the packet header to thecontroller.

In this example, the controller is configured to receive the packetheader, compare the packet header to a data store that represents thetopology of the network, use the values in the received header tocompute a physical path from the first switch to the radio device, senda flow table entry to the first switch, send a flow table entry to thesecond switch, send a flow table entry to the switch at the radio basestation, and send a flow table entry to the radio device.

In this example, the first switch is configured to: generate asubstitute data based at least in part on the flow table entry receivedfrom the controller in response to the first packet header, and transmitthe substitute data to the second switch. The first switch is furtherconfigured to: receive a second and subsequent packets identified byfinding a match in the flow table and transmit the substitute data tothe second switch immediately without additional instructions from thecontroller.

In this example, the second switch is configured to: receive thesubstitute data from the first switch and compare the substitute data toa flow table. Upon finding a match, the second switch is configured toforward the substitute data in the way indicated in the flow table to athird switch.

In this example, the third switch is configured to: receive substitutedata and compare the substitute data to a flow table. When the flowtable indicates forwarding to a radio device, the third switch sends thesubstitute data to the base station radio for transmission to the radiodevice.

In this example, the radio device is configured to: receive substitutedata over the radio link, look up the substitute data in a flow table todetermine how to handle the received data, and process that data into ausable stream. The radio device is further configured to transmit datato the base station. The radio device is further configured to determinevia procedures with the base station when and how to transmit data. Theradio device is further configured to send a request to the controller.This request may be sent via a configured Label Switched Path or via aconnection service to a particular network address. The radio device isfurther configured to receive from the controller a signal and an entryin a flow table for that connection. The radio device is furtherconfigured to prepare payloads to send by adding a label received fromthe controller that is in the same form as the substitute data used bynetwork switches to forward information along a virtual circuit.

The above-described embodiments including the drawings are examples ofthe invention and merely provide illustrations of the invention. Otherembodiments will be obvious to those skilled in the art. Thus, the scopeof the invention is determined by the appended claims and their legalequivalents rather than by the examples given.

INDUSTRIAL APPLICABILITY

The invention has application to the communications industry.

What is claimed is:
 1. A method of transporting data on a network, themethod comprising the steps of: providing network access linkscomprising a plurality of switches, the plurality of switches comprisinga first switch; receiving a first packet via an Internet Protocolsession from a first end-user device, the receiving performed at thefirst switch, the first packet comprising a first header comprising anInternet Protocol header, the Internet Protocol header comprising anInternet Protocol address; terminating the Internet Protocol session,said terminating taking place at the first switch; removing the InternetProtocol header from the first packet; matching the first packet withflow-path data in a flow-table; identifying a physical path using theflow-path data matched to the first packet, the physical path comprisinga transport route from the first switch to a second end-user device;generating a substitute packet at the first switch, the substitutepacket comprising: information from the first packet, said informationcomprising information remaining after removal of Internet Protocolheader; a path identifier comprising an instruction on how to route thesubstitute packet to the physical path in the plurality of switches tothe second end-user device; a connection identifier configured to permitidentifying multiple communications sessions that share the physicalpath from the first switch through the plurality of switches to thesecond end-user device; and control information comprising instructionson coordinating a joint operation of the first switch and the secondend-user device; transmitting the substitute packet along the physicalpath through the plurality of switches to the second end-user device;causing the second end-user device to: terminate the physical path forthe substitute packet; match the connection identifier of the substitutepacket to a communications session; and process the substitute packetinto a usable stream, the usable stream formed to exclude the InternetProtocol header previously removed from the first packet.
 2. The methodof claim 1, further comprising the step of receiving a usable datastream comprising a plurality of packets.
 3. The method of claim 2,wherein the usable data stream further comprises an audio stream.
 4. Themethod of claim 2, wherein the usable data stream further comprises avideo stream.
 5. The method of claim 2, wherein the usable data streamfurther comprises application data to be delivered to an application. 6.The method of claim 1, wherein the transport route is a virtual circuitselected from the group consisting of a Multi-Protocol Label Switched(MPLS) path, an Ethernet subnet, a Frame Relay data link connection, andan Asynchronous Transfer Mode (ATM) virtual path.
 7. The method of claim1, wherein the first packet further comprises a second header, thesecond header comprising a transport-layer protocol header, and themethod further comprising the steps of: terminating a transport-layerprotocol session; and deleting the second header when generating thesubstitute packet.
 8. The method of claim 1, wherein the first packetfurther comprises one or more additional headers representinghigher-level protocols; the method further comprising the steps of:terminating each protocol session corresponding to the one or moreadditional headers; and removing at the first switch the one or moreadditional headers prior to generating the substitute packet.
 9. Themethod of claim 1, wherein the first packet further comprises a payloadof information.
 10. The method of claim 9, further comprising the stepof transmitting the payload of information to the second end-user devicewith the substitute packet.
 11. The method of claim 1, furthercomprising the steps of: receiving a frame at any switch in theplurality of switches; and enabling each switch in the plurality ofswitches to match the frame with flow-path data in the flow-table. 12.The method of claim 11, further comprising the step of discarding theframe when any of the plurality of switches fails to match the framewith flow-path data in the flow-table.
 13. The method of claim 11,further comprising the step of sending an error message to the firstswitch when any switch in the plurality of switches fails to match theframe with flow-path data in the flow-table.
 14. The method of claim 11,further comprising the step of broadcasting a query seeking a flow-pathto the second end-user device when any of the plurality of switchesfails to match either the first packet or the substitute packet, withflow-path data, the broadcasting made to a connected device, theconnected device selected from the group consisting of a router, a host,a switch, and a controller.
 15. The method of claim 11, furthercomprising the step of enabling a connection of the second end-userdevice to one of the switches in the plurality of switches, theconnection selected from the group consisting of an optical cable, anelectrical cable, and a radio link.
 16. The method of claim 15, furthercomprising the steps of: receiving at the first switch a transmissionoriginating from a second end-user device, the transmission comprising apath identifier and a connection identifier, the transmission employinga header format defined in the substitute packet; matching thetransmission from the second end-user device with second flow-path datain the flow-table, the second flow-path data comprising a transportroute from the first switch to the first end-user device; generating asecond packet at the first switch, the second packet comprisinginformation from the transmission received from the second end-userdevice; adding to the second packet an Internet-Protocol-address headerthat participates in the Internet Protocol session terminated at thefirst switch after receiving the first packet from the first end-userdevice and a header for each higher-level protocol session terminatedfrom the first packet; and sending the second packet out of theplurality of switches to the first end-user device, the first end-userdevice selected from the group consisting of a terminal, a host, arouter, a switch, and a bridge.
 17. The method of claim 16, furthercomprising the step of limiting the connection identifier to oneselected from the group consisting of a Multi-Protocol Label Switched(MPLS) network Label, an Ethernet header, a Frame Relay Data LinkConnection Identifier, and an Asynchronous Transfer Mode (ATM) networkVirtual Path Identifier.
 18. A method of transporting data on networkaccess links from a first switch to an end-user device that is remotefrom the first switch, the method comprising the steps of: providingnetwork access links comprising a plurality of switches, the pluralityof switches comprising a first switch; receiving a first packet at thefirst switch, the first packet comprising data, the data comprising aplurality of packet headers, the plurality of packet headers comprisinga network-layer protocol, the network-layer protocol comprising anInternet Protocol address; creating a reduced data packet by terminatinga higher-level protocol at the first switch and removing from the firstpacket at least one packet header in the plurality of packet headersother than the network-layer protocol comprising the Internet Protocoladdress; generating a substitute packet at the first switch, thesubstitute packet comprising: the reduced data packet; and a substituteheader, the substitute header comprising: a connection identifiercomprising an instruction to identify a communication session; andcontrol information comprising instructions on coordinating a jointoperation of the first switch and the end-user device; transmitting thesubstitute packet via Internet Protocol routing using the InternetProtocol address to the end-user device; and enabling the end-userdevice to: derive a connection identity from the connection identifierand control information in the substitute header; and process thesubstitute packet into a usable stream.